Hey, thanks for looking into this! The root cause here is actually that run.sh is missing set -euo pipefail at the top, which most of our newer modules already use (claude-code, aider, amazon-q, agent-firewall, dotfiles, etc.). Adding that one line would make the manual if ! guards unnecessary since the script would automatically exit on any non-zero return, and it'd also catch other silent failures we're not handling today (like git clone itself failing, or the base64 -d pipe breaking).

@ikkz Would you be open to swapping the approach to just add set -euo pipefail at the top instead? Smaller diff, catches more cases, and brings this module in line with the rest of the registry.

@DevelopmentCats Updated as suggested.

Added set -euo pipefail to run.sh instead of manually checking the pre/post-clone script exit codes, and added regression tests for failing pre/post-clone hooks.

Also, once this PR is merged, when should we expect the new git-clone module version (v1.3.1) to be published?

@DevelopmentCats Updated as suggested.

Added set -euo pipefail to run.sh instead of manually checking the pre/post-clone script exit codes, and added regression tests for failing pre/post-clone hooks.

Also, once this PR is merged, when should we expect the new git-clone module version (v1.3.1) to be published?

Once we merge this PR I will immediately go and release this Module and it should be available a few minutes after that.

@ikkz Should show up on the registry within the next 10 mins.

Thank you! Much appreciated.